Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: adding clickble symbol render in chat panel #3420

Open
wants to merge 16 commits into
base: main
Choose a base branch
from

Conversation

Sma1lboy
Copy link
Collaborator

@Sma1lboy Sma1lboy commented Nov 14, 2024

Feature

  • Implemented onNavigateSymbol with rendered inline blocks.
  • Implemented onHoverSymbol with rendered inline blocks.
  • Both ClientApi methods are handled by a capability check.
  • Inline code blocks will not be rendered as clickable if onNavigateSymbol is not exposed.
  • The Go to definition title will not be shown if onHoverSymbol is not implemented.

Demo

Screen.Recording.2024-11-30.at.06.37.15.mov

@wsxiaoys wsxiaoys changed the title feat: adding clickble keyword render in chat panel feat: adding clickble symbol render in chat panel Nov 18, 2024
@wsxiaoys
Copy link
Member

Need handle cases that certain backend doesn't support such feature (e.g IntelliJ)

@Sma1lboy Sma1lboy force-pushed the feat-adding-clickble-keywords-chat-panel branch from ddcbe91 to c3d0709 Compare November 30, 2024 10:32
The code changes in `ChatPage` component add support for the `onNavigateSymbol` and `onHoverSymbol` capabilities. These capabilities are checked and set using the `hasCapability` method of the server. The `onNavigateSymbol` and `onHoverSymbol` methods are conditionally used based on the support for these capabilities. This change enhances the functionality of the ChatPage component in the Tabby UI.
@Sma1lboy Sma1lboy marked this pull request as ready for review November 30, 2024 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants